Keep STC tpattern sample within TR#300
Merged
Merged
Conversation
3dTshift rejects offsets >= TR. The sample list 0.1*i overflowed TR=2.0s once num_slices > 20.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
test_slice_timing_tpattern_listintegration test has been failing on main since the niwrap bump (#299). The sample tpattern was[0.1 * i for i in range(num_slices)]withtr=2.0, so oncenum_slices > 20the offsets crossed the TR boundary and AFNI 24.2.06's3dTshiftbailed withIllegal value 2.1 in tpattern file.Switched the sample to
i * tr / num_slicesso it always sweeps[0, tr), which is what real slice timings look like anyway. The test only cares that a list is accepted, so the exact values don't matter.Test plan